Skip to content

release: v1.4.1 → main#853

Merged
philanton merged 3 commits into
mainfrom
release/v1.4.1
Jun 18, 2026
Merged

release: v1.4.1 → main#853
philanton merged 3 commits into
mainfrom
release/v1.4.1

Conversation

@philanton

@philanton philanton commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

v1.4.1

Patch release.

Bug Fixes

Notes

  • nitronode-only fix. SDK packages (@yellow-org/sdk, sdk-compat, sdk-mcp) version-bumped to 1.4.1 for strict mirror but not republished to npm — no SDK code changed since v1.4.0.
  • No mcp-v tag.

Artifacts

Docker images (ghcr.io/layer-3/nitrolite, tag v1.4.1) — nitronode, faucet-app, playground.

Summary by CodeRabbit

  • Chores
    • Updated version to 1.4.1 across all packages and services.

philanton and others added 3 commits June 18, 2026 12:07
## Release v1.4.0

### Highlights
- **Audit remediation — MF3 final round (#846):** security hardening
across contracts, nitronode, SDK, and RPC.
- Contract: reentrancy guard + event-handler monotonicity, reorg
double-spend confirmation gate.
- **Breaking:** removed app registry, action allowances, user staking,
and rebalance feature; removed SDK locking client + app-registry ABI;
RPC surface (`docs/api.yaml`) trimmed.
- DoS/overflow fixes: pagination limit=0, uint8 quorum overflow,
frame-layer rate limit, deposit-state enforcement.
- feat(nitronode): add USDC asset across 7 chains (#845)
- fix(go-sdk): preserve channel challenge expiry (#816)
- Fix SDK MCP Hono audit failure (#821)
- Dependency bumps (gomod, npm, ws).

### Versioning note
Minor bump (1.3.1 → 1.4.0). Note: removal of
app-registry/staking/rebalance + RPC methods is a breaking change for
downstream consumers — flagged here rather than a major bump per 1.x
cadence.

### MCP
`mcp-v1.4.0` tag intentionally NOT pushed this release.
`@yellow-org/sdk-mcp` published manually (npm + MCP registry), alongside
manual `@yellow-org/sdk` + `@yellow-org/sdk-compat` publishes.
Patch release for nitronode blockhash fix (#851). Bump npm package
versions, MCP server.json, and chart appVersions to 1.4.1 (strict mirror).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5953ec17-2d6f-428a-bb17-99f931a3f91d

📥 Commits

Reviewing files that changed from the base of the PR and between a336dd4 and c6ca1aa.

⛔ Files ignored due to path filters (4)
  • sdk/mcp/mcp-publisher.tar.gz is excluded by !**/*.gz
  • sdk/mcp/package-lock.json is excluded by !**/package-lock.json
  • sdk/ts-compat/package-lock.json is excluded by !**/package-lock.json
  • sdk/ts/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (8)
  • faucet-app/chart/Chart.yaml
  • nitronode/chart/Chart.yaml
  • playground/chart/Chart.yaml
  • sdk/mcp/mcp-publisher
  • sdk/mcp/package.json
  • sdk/mcp/server.json
  • sdk/ts-compat/package.json
  • sdk/ts/package.json

📝 Walkthrough

Walkthrough

Version bump from 1.4.0 to 1.4.1 across seven files: three Helm chart appVersion fields (faucet-app, nitronode, playground) and four SDK version fields (sdk/ts/package.json, sdk/ts-compat/package.json, sdk/mcp/package.json, and both version entries in sdk/mcp/server.json).

Changes

Version bump 1.4.0 → 1.4.1

Layer / File(s) Summary
SDK package and server version bumps
sdk/ts/package.json, sdk/ts-compat/package.json, sdk/mcp/package.json, sdk/mcp/server.json
version field updated from 1.4.0 to 1.4.1 in all SDK packages; sdk/mcp/server.json has both root and packages[] version entries updated.
Helm chart appVersion bumps
faucet-app/chart/Chart.yaml, nitronode/chart/Chart.yaml, playground/chart/Chart.yaml
appVersion updated from "1.4.0" to "1.4.1" in all three Helm charts.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • layer-3/nitrolite#596: Bumps the same sdk/ts-compat/package.json and sdk/ts/package.json version fields, targeting a different version (1.1.0).
  • layer-3/nitrolite#798: Updates the identical set of Helm appVersion fields and SDK version fields as this PR, part of the same version-bump line of work.
  • layer-3/nitrolite#850: Directly modifies the same seven version fields across the same files as this PR.

Suggested reviewers

  • ihsraham
  • nksazonov
  • dimast-x

Poem

🐇 Hop, hop, a patch release today,
From one-four-zero we bounce away,
Seven files ticked, each version aligned,
No logic changed, just numbers refined,
The rabbit stamps 1.4.1 with glee! 🎉

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'release: v1.4.1 → main' directly describes the pull request's primary objective: merging the v1.4.1 release into the main branch, matching the PR objectives of releasing patch version 1.4.1.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v1.4.1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@philanton philanton merged commit 9e970a2 into main Jun 18, 2026
22 of 23 checks passed
@philanton philanton deleted the release/v1.4.1 branch June 18, 2026 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant